Skip to content

ci: update to Changesets CLI v3 for changesets/action v2, and revert the unpublished 2.3.4 - #293

Merged
alexander-akait merged 3 commits into
mainfrom
ci/changesets-action-v1
Nov 13, 2026
Merged

alexander-akait merged 3 commits into
mainfrom
ci/changesets-action-v1

Conversation

@alexander-akait

@alexander-akait alexander-akait commented Nov 13, 2026 •

Copy link
Copy Markdown
Member

Summary

2.3.4 was versioned by #292 but never published: npm and the GitHub releases still show 2.3.3 as latest.

#290 bumped changesets/action from v1.9.0 to v2.1.2, a major version. v2 only works with Changesets CLI v3, and tapable was on @changesets/cli v2, so the Release workflow stops before publishing:

##[error]This version of the Changesets action is designed to work with Changesets CLI v3. Changesets CLI v2 is not supported; use Changesets action v1 instead, which is compatible with CLI v2.

v2 also renamed the inputs, so this workflow's inputs were ignored there.

This keeps action v2 and updates the rest to match, the same setup webpack runs:

  • Dependencies: @changesets/cli ^3 and @changesets/get-github-info ^1. The $schema in .changeset/config.json now points at @changesets/config 3.1.4.
  • .changeset/changelog-generator.mjs moves to get-github-info v1's API: getInfo/getInfoFromPullRequest became getCommitInfo/getPullRequestInfo, which return markdownLinks. It's now the same file as webpack's, which also retries GitHub lookups so a transient API drop doesn't fail a release.
  • release.yml keeps changesets/action v2.1.2 with its renamed inputs:
    • version → version-script
    • publish → publish-script
    • commit → commit-message
    • title → pr-title
    • the GITHUB_TOKEN env becomes the github-token input
  • The unpublished 2.3.4 is reverted: package.json goes back to 2.3.3, the 2.3.4 CHANGELOG entry is removed, and the two changesets chore(release): new release #292 consumed (fix: type the call and loop interceptor arguments as the hook's own #288 and fix: declare TypedHookMap as an interface #291) are restored. Once this merges, the Release workflow opens the release pull request again with CLI v3. Merging that one publishes 2.3.4.

What kind of change does this PR introduce?

ci

Did you add tests for your changes?

No, this is CI, dev dependencies and release metadata only.

  • npm run lint and npm test pass.
  • CLI v3 reads the config: changeset status lists tapable as a pending patch from the restored changesets.
  • The new changelog generator loads and exports both functions.

The release pull request the workflow opens after this merges is the full check.

Does this PR introduce a breaking change?

No. Only CI, dev dependencies and unpublished release metadata change.

If relevant, what needs to be documented once your changes are merged or what have you already documented?

n/a

Use of AI

Written with Claude Code (diagnosis from the Release job logs, the migration following webpack's setup, the release revert and this description), directed and reviewed by me.

🤖 Generated with Claude Code

https://claude.ai/code/session_01HArJAXZagrHVVNLZZk9soh

Summary by CodeRabbit

  • Chores
    • Updated release automation inputs and Changesets tooling.
  • Bug Fixes
    • Release notes now retry GitHub lookups after temporary failures, helping preserve commit, pull request, and author links.
    • Updated release note formatting and the Changesets schema reference.
  • Documentation
    • Added patch release notes covering TypedHookMap interface typing and interceptor argument types.

v2 only works with Changesets CLI v3, and tapable is on @changesets/cli v2, so
the Release workflow fails before publishing ("Changesets CLI v2 is not
supported; use Changesets action v1 instead") and 2.3.4 never reached npm.
@changeset-bot

changeset-bot Bot commented Nov 13, 2026 •

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: fa6d12a

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
tapable Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@coderabbitai

coderabbitai Bot commented Nov 13, 2026 •

Copy link
Copy Markdown

Explain Change →

No actionable comments were generated in the recent review.

Walkthrough

The release workflow passes the GitHub token and renamed inputs to the Changesets action. The Changesets CLI and GitHub-info dependency versions and schema reference are updated. The changelog generator retries commit and pull-request lookups, normalizes lookup results into nullable links, and uses those links when formatting release lines.

Merge Risk: Minimal · up to fa6d1

This change updates the release tooling and restores the unpublished 2.3.4 changes so the next release run can proceed. No concrete merge-blocking issue was identified. The post-merge Release run is the real check, since the action's behavior is not exercised before merge.

Pre-merge checks: Passed 4

Check name Status Explanation
Title check Passed The title names two changes: the move to Changesets CLI v3 for changesets/action v2, and the revert of the unpublished 2.3.4 release. The main change is the CLI v3 and workflow update, which the summa…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Full details: Title check

Explanation

The title names two changes: the move to Changesets CLI v3 for changesets/action v2, and the revert of the unpublished 2.3.4 release. The main change is the CLI v3 and workflow update, which the summary and objectives confirm. The revert is a real part of the changeset (the CHANGELOG entry removal and the version change to 2.3.3). The title is specific and accurate, and it is a single sentence, though it is somewhat long at 90 characters.

Finishing Touches

Generate unit tests (beta)

  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

Recent review info

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: dd9b4bd5-21cf-48f0-873f-97b05230941e
Commits

Reviewing files that changed from the base of the PR and between 431b587 and fa6d12a.

Files ignored due to path filters: 1

  • package-lock.json is excluded by !**/package-lock.json
Files selected for processing: 4

  • .changeset/typed-hook-map-interface.md
  • .changeset/typed-interceptor-arguments.md
  • CHANGELOG.md
  • package.json
Files with no reviewable changes: 1

  • CHANGELOG.md

Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 5 remain after this review.

changesets/action v2 only works with Changesets CLI v3, so the Release
workflow stopped before publishing. Instead of pinning the action back:

- @changesets/cli ^3 and @changesets/get-github-info ^1; the changelog
  generator moves to its getCommitInfo/getPullRequestInfo API, as webpack's did
- the workflow keeps changesets/action v2.1.2 with its renamed inputs
  (github-token, version-script, publish-script, commit-message, pr-title)
@alexander-akait alexander-akait changed the title ci: pin changesets/action back to v1.9.0 ci: update to Changesets CLI v3 for changesets/action v2 Nov 13, 2026
@socket-security

socket-security Bot commented Nov 13, 2026 •

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updated@​changesets/​cli@​2.31.1 ⏵ 3.0.399 +210074 -2591 -3100
Updated@​changesets/​get-github-info@​0.8.0 ⏵ 1.0.1100 +210090 -893 +8100

View full report

#292 versioned 2.3.4, but the Release workflow failed before publishing it.
Restore its changesets, the 2.3.3 version and the changelog, so the fixed
workflow opens the release pull request again once this merges.
@alexander-akait alexander-akait changed the title ci: update to Changesets CLI v3 for changesets/action v2 ci: update to Changesets CLI v3 for changesets/action v2, and revert the unpublished 2.3.4 Nov 13, 2026
@codecov

codecov Bot commented Nov 13, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.25%. Comparing base (10e336b) to head (fa6d12a).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #293   +/-   ##
=======================================
  Coverage   99.25%   99.25%           
=======================================
  Files          15       15           
  Lines         805      805           
  Branches      140      140           
=======================================
  Hits          799      799           
  Misses          6        6           
Flag Coverage Δ
integration 99.25% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@codspeed

codspeed Bot commented Nov 13, 2026

Copy link
Copy Markdown

Merging this PR will not alter performance

1 warning

⚠️ 4 benchmarks are dominated by system calls

System calls cannot be simulated consistently and are left out of the measure. The reported value understates the real cost. Switch to the Walltime instrument to measure them.

Learn more about system calls

See affected benchmarks

✅ 92 untouched benchmarks


Comparing ci/changesets-action-v1 (fa6d12a) with main (10e336b)

Open in CodSpeed

@alexander-akait
alexander-akait merged commit 1b05d18 into main Nov 13, 2026
36 checks passed
@alexander-akait
alexander-akait deleted the ci/changesets-action-v1 branch November 13, 2026 15:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant